Skip to content

Conversation

asit2004
Copy link

@asit2004 asit2004 commented Oct 1, 2025

Description

This PR removes the @scarf/scarf dependency from swagger-ui and related packages.
fixes #10573

Motivation and Context

This change removes the @scarf/scarf dependency, which was only used for analytics.
• Lifecycle script–based analytics do not work with pnpm and bun, which block such scripts by default.
• Many npm users also enable ignore-scripts for security, making analytics data incomplete.
• Removing this dependency improves compatibility, security posture, and removes unnecessary overhead without affecting Swagger UI functionality.

How Has This Been Tested?

•	Ran npm install after removal to regenerate lockfile.
•	Ran npm run build successfully.
•	Ran npm start to confirm Swagger UI runs correctly.
•	Verified that @scarf/scarf is no longer present in package.json, package-lock.json, or node_modules.

Screenshots (if appropriate):

N/A – no UI changes.

Checklist

My PR contains...

  • No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
  • Dependency changes (any modification to dependencies in package.json)
  • Bug fixes (non-breaking change which fixes an issue)
  • Improvements (misc. changes to existing features)
  • Features (non-breaking change which adds functionality)

My changes...

  • are breaking changes to a public API (config options, System API, major UI change, etc).
  • are breaking changes to a private API (Redux, component props, utility functions, etc.).
  • are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
  • are not breaking changes.

Documentation

  • My changes do not require a change to the project documentation.
  • My changes require a change to the project documentation.
  • If yes to above: I have updated the documentation accordingly.

Automated tests

  • My changes can not or do not need to be tested.
  • My changes can and should be tested by unit and/or integration tests.
  • If yes to above: I have added tests to cover my changes.
  • If yes to above: I have taken care to cover edge cases in my tests.
  • All new and existing tests passed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove @scarf/scarf dependency
1 participant